[v3-3-test] Relax aiosqlite cap. Support aiosqlite>=0.20.0 (#69796) - #69979
Merged
Conversation
aiosqlite 0.22.0 had a hanging pytest session bug (aiosqlite#369) and also triggered a hanging helper thread under SQLAlchemy 2 (sqlalchemy#13039). The pytest issue was fixed in 0.22.1, and the SQLAlchemy-side fix shipped in 2.0.46. Since our SQLAlchemy floor is already >=2.0.48, we can safely relax the cap from <0.22.0 to !=0.22.0 (excluding only the known-bad 0.22.0 release). Part of #69616. (cherry picked from commit f201f14) Co-authored-by: Arnav <a.purohit1903@gmail.com>
1 task
eladkal
marked this pull request as ready for review
July 16, 2026 17:06
Contributor
Author
|
Hi maintainer, this PR was merged without a milestone set.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
aiosqlite 0.22.0 had a hanging pytest session bug (aiosqlite#369) and also triggered a hanging helper thread under SQLAlchemy 2 (sqlalchemy#13039). The pytest issue was fixed in 0.22.1, and the SQLAlchemy-side fix shipped in 2.0.46. Since our SQLAlchemy floor is already >=2.0.48, we can safely relax the cap from <0.22.0 to !=0.22.0 (excluding only the known-bad 0.22.0 release).
Part of #69616.
(cherry picked from commit f201f14)
Co-authored-by: Arnav a.purohit1903@gmail.com